Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@airflow.apache.org
  Slack: https://s.apache.org/airflow-slack

This PR is meant to solve this issue I've opened: #32227

InvokeLambdaFunctionOperator now accepts bytes or str for its payload argument.
If the value is str, it is converted into bytes using encode() method.

This will fix incompatibility with corresponding boto3 functionality while not breaking the API.

You need to update the unit tests. But otherwise, LGTM

@eladkal @vincbeck can you refer me to the tests that should be updated?
Should I add some new once, and if so -- where?

@eladkal @vincbeck can you refer me to the tests that should be updated? Should I add some new once, and if so -- where?

Sure.

The hook is tested with string payload

you should add a new test / extend existed test to also test byte payload.
I think in this case probably just making the test accept multiple inputs (strings and bytes) using @pytest.mark.parametrize will do the trick (you can find many examples for this in the source code)

The same goes for testing the operator class

@eladkal pls take a another look

Static checks are failing

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.